Event driven permissive sharing of information

ABSTRACT

Event driven permissive sharing of information is disclosed. In an aspect, user equipment can include information sharing profiles that can facilitate sharing information with other devices or users, such as sharing location information. The information sharing profiles can include trigger values, such that when a target value transitions the trigger value, a permission value is updated to restrict or allow access to sharable information. As such, event driven permissive sharing of information allows for designation of temporary friend information sharing with user-defined triggers.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to each of,U.S. patent application Ser. No. 14/548,901, filed on 20 Nov. 2014,entitled “EVENT DRIVEN PERMISSIVE SHARING OF INFORMATION,” which is acontinuation of U.S. patent application Ser. No. 13/447,069, filed on 13Apr. 2012, now issued as U.S. Pat. No. 8,925,104, entitled “EVENT DRIVENPERMISSIVE SHARING OF INFORMATION.” The entireties of the foregoingapplications are hereby incorporated by reference herein.

TECHNICAL FIELD

The disclosed subject matter relates to permissive sharing ofinformation and, more particularly, to event driven permissive sharingof information.

BACKGROUND

By way of brief background, sharing of information, such as locationinformation for mobile devices, with other parties has included grantingpermission to share that information. As an example, a user candesignate other users as ‘friends’. These other friends would then bepermitted to access designated shared information.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an illustration of a system that facilitates event drivenpermissive sharing of information in accordance with aspects of thesubject disclosure.

FIG. 2 is a depiction of a system that facilitates event drivenpermissive sharing of information in accordance with aspects of thesubject disclosure.

FIG. 3 illustrates a system that facilitates event driven permissivesharing of information in accordance with the disclosed subject matter.

FIG. 4 is a depiction of a user interface that facilitates event drivenpermissive sharing of information in accordance with aspects of thesubject disclosure.

FIG. 5 is a depiction of a user interface that facilitates event drivenpermissive sharing of information in accordance with aspects of thesubject disclosure.

FIG. 6 illustrates a method facilitating event driven permissive sharingof information in accordance with aspects of the subject disclosure.

FIG. 7 illustrates a method for facilitating event driven permissivesharing of information in accordance with aspects of the subjectdisclosure.

FIG. 8 illustrates a block diagram of an exemplary embodiment of anevent driven permissive sharing of location information to implement andexploit one or more features or aspects of the subject disclosure.

FIG. 9 is a block diagram of an exemplary embodiment of a mobile networkplatform to implement and exploit various features or aspects of thesubject disclosure.

FIG. 10 illustrates a block diagram of a computing system operable toexecute the disclosed systems and methods in accordance with anembodiment.

DETAILED DESCRIPTION

The subject disclosure is now described with reference to the drawings,wherein like reference numerals are used to refer to like elementsthroughout. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the subject disclosure. It may be evident, however,that the subject disclosure may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to facilitate describing the subjectdisclosure.

In an embodiment, a system can include a memory and processor. Theprocessor can facilitate the execution of computer-executableinstructions stored on the memory. The execution of thecomputer-executable instructions can cause the processor to receiveinput for an information sharing profile. The processor can furtherassign values to a trigger value of the information sharing profile.Moreover, the processor can assign a value in the information sharingprofile designating sharable information. Additionally, the processorcan assign a value of the information sharing profile, the valuerelating to target users or target devices of the sharable information.Moreover, the processor can facilitate access to the information sharingprofile.

In another embodiment, a method can include accessing, by a system, asharing profile. The method can further include designating permissionvalue based on a trigger value, an information sharing designationvalue, and an identification value of the sharing profile. Moreover, themethod can facilitate access to information associated with theinformation sharing designation value of the sharing profile based onthe permission value.

In a still further embodiment, a mobile device can include a memorystoring computer-executable instructions and a processor thatfacilitates execution of the computer-executable instructions. Theseinstructions can cause the processor to receive input for an informationsharing profile. The processor can then assign a trigger value, whereina target value transitioning the trigger value is associated withrestricting the sharing of designated information. The processor canfurther assign a value that designates information as information forsharing with select devices or users. The processor can also assign avalue corresponding to the selection of devices or users that can beallowed access to the designated information. Further, the processor canfacilitate access to the information sharing profile. Moreover, theprocessor can restrict access to designated information based onpredetermined privacy criteria.

FIG. 1 is an illustration of a system 100, which facilitates eventdriven permissive sharing of information in accordance with aspects ofthe subject disclosure. System 100 can include user equipment (UE) 110.UE 110 can include a user interface (UI) component 112. UI component 112can be, for example, a touch screen interface on a mobile device, adisplay and discrete keypad on a laptop computer, a screen and a mousingdevice on a smartphone, etc.

System 100 can further include temporary friend sharing (TFS) profilecomponent 120. TFS profile component 120 can be included in UE 110. TFSprofile component 120 can be communicatively coupled with UI component112. As such, UI component 112 can be employed to interact with TFSprofile component 120. TFS profile component can further include TFSprofile value(s) 121. TFS profile value(s) 121 can include valuescomposing a TFS profile. The TFS profile, at least in part, can includevalues associated with event driven permissive sharing of information.The TFS profile can be a set of values that includes one or more subsetsof values that can comprise the same, partially the same, or differentvalues. UE 110 can facilitate access to TFS profile value(s) 121 bycarrier-side event driven permissive information sharing components,wherein carrier-side indicates that the component is part of the carriernetwork or closely associated therewith.

TFS profile component 120 can facilitate a user designating aspects of aTFS profile. The TFS profile can be stored on UE 110 or can be stored ona remote system, such as a carrier-side component. TFS profile caninclude designation of trigger event value(s), by way of TFS profilevalue(s) 121. A trigger event value can be correlated with automaticallytransitioning between permitting sharing of designated information andrestricting sharing of designated information. As an example, wheresharing location information is associated with a temporal trigger eventvalue, sharing of the location information can occur before the triggertime is reached and sharing of the location information can berestricted after the trigger time is reached. As such, TFS profilecomponent 120 can facilitate temporary sharing of location information.

Moreover, TFS profile can also include the designation of whatinformation can be shared. TFS profile can include designation of sharedinformation designation value(s), by way of TFS profile value(s) 121. Ashared information designation value can be associated withidentification of specific information or types of information that canbe accessed in accordance with the TFS profile. While nearly any type ofinformation can be shared, specific non-limiting examples of informationthat can be shared can include location information, mood, status,contact information, address book information, device information,profile information, program data, etc. As a more specific non-limitingexample, a user can designate by way of TFS profile component 120 thatthe UE location, address book, and Shared_Ideas.doc file can be sharedwhere the trigger event value has not been transitioned.

Furthermore, TFS profile can include the designation of accesspermissions. Access permissions can designate the identification ofsystems or users that can access shared information where the triggerevent value has not been transitioned. As such, a user can designate, byway of TFS profile value(s) 121, another user or device as a permittedto access shared information. As an example, a user can designate thather husband can access shared information from any other device. As asecond example, a user can designate that anyone can access sharedinformation from a single terminal at his place of employment, such asby designating a specific static IP address, MAC address, stored key,etc. As a third example, a user can designate that his mom or dad canaccess shared information from their smartphones. Numerous otherexamples are within the scope of the present disclosure but are notrecited for clarity and brevity.

In a further aspect, other TFS profile value(s) 121 can be designated.Other TFS profile value(s) 121 can be nearly any type of value. As anexample, TFS profile value(s) 121 can be associated with predefinedevent driven permissive information sharing schemes to facilitate simpleselection of predefined values through selection of a scheme, such as a‘professional scheme’, a ‘non-professional scheme’, a ‘family scheme’,etc. In another example, TFS profile value(s) 121 can be associated withlevels of granularity for data sharing, such as, sharing locationinformation restricted to a city level, street level, address level,radius level, etc. As a further example, TFS profile value(s) 121 can beassociated with hierarchical event driven permissive informationsharing, such as, designating that the types of information to be sharedshould mirror that shared by the party being shared with, designatingthat a second user can designate a third user to share your informationwith but only at a more restricted level, etc.

In another aspect, TFS profile component 120 can be communicativelycoupled with other UE 110 components to facilitate integration of sharedinformation. As an example, where a first user can designate that hewill share his UE location with a second user until April 7, thisinformation can be shared with the first user's UE address bookcomponent such that the address card for the second user indicates thatthe ‘friend’ status will automatically terminate on April 7. As a secondexample, an application on a UE related to building and reflecting ofsocial networks or social relations among people, who, for example,share interests and/or activities (a ‘social networking application’),can be communicatively coupled with TFS profile component 120.Continuing the example, where a first user designates the same seconduser as a temporary friend more than three times, the social networkingapplication can query the first user about adding the second user as a‘long term friend’ in said social networking application.

FIG. 2 is a depiction of a system 200 that can facilitate event drivenpermissive sharing of information in accordance with aspects of thesubject disclosure. System 200 can include UE 210. UE 200 can compriseTFS profile component 220. TFS profile component 220 can designateaspects of a TFS profile. The TFS profile can be stored on UE 210 or canbe stored on a remote system, such as a carrier-side component. UE 210can be communicatively coupled with event driven permissive informationsharing component 230 to facilitate event driven permissive sharing ofinformation in accordance with aspects of the subject disclosure.

UE 210 can also be communicatively coupled with permissive informationsharing component 240, to facilitate non-event driven permissive sharingof information that comports with more conventional information sharingsystems, thereby facilitating backwards-compatibility for legacy supportof more conventional systems. As such, permissive information sharingcomponent 240 can be communicatively coupled to Friend UE 260. Friend UE260 can access information shared under more conventional informationsharing systems and, as such, would be associated with non-event drivenpermissions. As an example, UE 210 can acknowledge a friend relationshipassociated with sharing location information between UE 210 and FriendUE 260 by way of permissive information sharing component 240 wherein,without further user action, it would be expected that sharing locationinformation would continue over the long term.

In an aspect, event driven permissive information sharing component 230can be communicatively coupled to permissive information sharingcomponent 240. As such, event driven permissive information sharingcomponent 230 can interact with permissive information sharing component240 to create a more conventional ‘long term’ friend relationship by wayof permissive information sharing component 240. Further, event drivenpermissive information sharing component 230 can interact withpermissive information sharing component 240 to automatically alter orremove the more conventional ‘long term’ friend relationship by way ofpermissive information sharing component 240, thus, in a manner, actingas a surrogate actor for a user of UE 210. As such, in some embodiments,the event driven process can at least create, alter, and destroy aconventional friend relationship to allow the use of event-drivenrelationship, e.g., temporary friend relationships, on legacy systems.As such, permissive information sharing component 240 can also becommunicatively to temporary friend UE 252. When a trigger event valuehas been transitioned event driven permissive information sharingcomponent 230 can automatically alter or destroy the conventional friendrelationship by way of permissive information sharing component 240 torestrict information sharing with temporary friend UE 252. In anembodiment, permissive information sharing component 240 can be acarrier-side component.

In a further aspect, event driven permissive information sharingcomponent 230 can be communicatively coupled to temporary friend UE 250.As such, shared information can be accessed by temporary friend UE 250while a trigger event value has not been transitioned. When the triggerevent value has been transitioned, information sharing can beautomatically restricted. In an embodiment, event driven permissiveinformation sharing component 230 can be a carrier-side component.

In an aspect, TFS profile component 220 can be the same as or similar toTFS profile component 120. As such, TFS profile component 220 canfacilitate a user designating aspects of a TFS profile, such asdesignating an event driven relationship between UE 210 and temporaryfriend UE 250, temporary friend UE 252, etc. Each event drivenrelationship can be associated with a trigger event value facilitatingautomatic updating of the status of the event-driven relationship. Thiscan facilitate formation of temporary friend relationships that canautomatically expire in response to the trigger event occurring. TFSprofile component 220 can also facilitate the designation of whatinformation can be shared, such as sharing of limited sets ofinformation with temporary friends. Furthermore, a TFS profile caninclude the designation of access permissions to facilitate the sharinginformation with designated UEs or Users.

FIG. 3 illustrates a system 300 that facilitates event driven permissivesharing of information in accordance with aspects of the subjectdisclosure. System 300 can include UE 310. UE 310 can include TFSprofile component 320. UE 310 can be communicatively coupled with eventdriven permissive information sharing component 330. In some embodimentsTFS profile component 320 can be the same as or similar to TFS profilecomponent 120 or 220. As such, TFS profile component 320 can facilitatea user designating aspects of a TFS profile by way or UE 310, such asdesignating an event driven relationship. Event driven relationships canbe associated with a trigger event value facilitating automatic updatingof the status of the event-driven relationship. TFS profile component320 can also facilitate the designation of access permissions, such asthose related to the sharing information with designated UEs or Users.Furthermore, TFS profile component 320 can facilitate the designation ofwhat information can be shared, such as sharing of limited sets ofinformation with temporary friends.

In an aspect, TFS profile component 320 can facilitate designation oflocation information as shareable information by way of locationcomponent 322. Location component 322 can facilitate designating whatlocation information is accessible in a temporary friend relationshipprior to the trigger event occurring. Sharing location information canbe designated to only include certain types of information, locationinformation at certain levels of granularity, sharing locationinformation only during scheduled times, etc. As an example, locationcomponent 322 can facilitate designating sharing of location informationno finer than the city level between the hours of 9 am and p.m., Mondayto Friday.

In a further aspect, TFS profile component 320 can facilitatedesignation of schedule information as shareable information by way ofschedule component 324. Schedule component 324 can facilitatedesignating what schedule information is accessible in an event drivenrelationship prior to a trigger event occurring. Schedule informationcan be related to a user's schedule, such as appointments and events.Shared schedule information can be limited by schedule component 324,for example by limiting sharing to title only, e.g., event details arenot shared; by sharing select classes of schedule information, e.g.,work schedule can be shared but personal schedule is not shared; bysharing schedule information for only certain time periods, e.g.,sharing the schedule from 9 am,-5 pm, Monday to Friday but restrictingaccess to all other periods, etc. As an example, schedule component 324can facilitate designating sharing of schedule information from a workschedule only and only from the date the event driven relationship wascreated and only up to the anticipated expiration date of the eventdriven relationship where the trigger is a date trigger.

In another aspect, TFS profile component 320 can facilitate designationof services information as shareable information by way of servicescomponent 326. Services component 326 can facilitate designating whatservices information is accessible in an event driven relationship priorto a trigger event occurring. Services information can include anyinformation associated with services running on UE 310. A service caninclude software in execution or software accessing services associatedwith UE 310. As such, services can include email, text messaging, SMSservice, GPS applications, word processor applications, spreadsheetapplications, digital music applications, etc. Sharing informationassociated with services can facilitate sharing service data or dataaccessed by a service. As an example, services component 326 canfacilitate designating sharing of services information for a digitalmusic service allowing, for instance, sharing of what music is currentlyplaying or sharing of music from a digital music library associated withthe digital music service. As a second example, s component 326 canfacilitate designating sharing of services information for a digitalcamera application of UE 310 facilitating access to photographs taken bythe digital camera application until a trigger event occurs.

TFS profile component 320 can further include privacy component 328.Privacy component 328 can facilitate restricting access to informationthat can otherwise be permissible by other components of TFS profilecomponent 320. Privacy component 328 can analyze, for example,information before allowing access to the information from anotherdevice or user in an event driven relationship with UE 310. As anexample, UE 310 can be in an event driven information sharingrelationship with another UE that allows sharing of audio recordingsmade with UE 310. Continuing the example, privacy component 328 caninclude restriction of access to information related to UE 310 user'sfamily. Where a recoding is accidentally made of a phone call with UE310 the user's wife, privacy component 328 can restrict access to thatrecording where it otherwise might have been made accessible under theevent driven information sharing relationship.

FIG. 4 is a depiction of an exemplary user interface 400 thatfacilitates event driven permissive sharing of information in accordancewith aspects of the subject disclosure. User interface 400 can be aninterface related to interacting with data for a contact. The contactcan include a name, title, company, phone number, etc., as is common inthe art. The contact user interface can further include actionsassociated with interacting with the contact, such as starting a textmessaging procedure when “text message” is selected on the contact userinterface 400, as is common in the art. The contact user interface 400can further include a first information and interaction segment 410. Thefirst information and interaction segment 410 can present informationrelated to an event driven permissive information sharing relationship.As an example, the first information and interaction segment 410illustrates that a trigger has been set for 12 a.m. on 26 Jul. 2012. Thefirst information and interaction segment 410 also illustrates that thetrigger can be altered, which can be initiated by tapping the firstinformation and interaction segment 410 where user interface 400includes a touch screen interface.

Further actions can be induced by taping on, for example, a secondinformation and interaction segment 412. The second information andinteraction segment 412 can be related to an action for accessing sharedlocation information. The shared location information can be locationinformation designated for sharing where a trigger value has not beentransitioned. Other information designated for sharing can be accessed,for example, by taping on a third information and interaction segment414. The third information and interaction segment 414 can be related toan action for accessing other types of designated shared information.Other information designated for sharing, can include, for example,schedule information, services information, etc. Exemplary userinterface 400 in not meant to be an exhaustive example of a contactoriented user interface facilitating event driven permissive sharing ofinformation in accordance with aspects of the subject disclosure.Numerous other user interface elements or permutations of thosepresented can be included in nearly any combination to facilitate accessto the various designated shared information subject to a systemtransitioning of a trigger value. While the first information andinteraction segment 410 illustrates a temporal trigger, other types oftrigger values can be employed, such as, locations, event counts,proximities values, etc.

FIG. 5 is a depiction of a user interface 500 that facilitates eventdriven permissive sharing of information in accordance with aspects ofthe subject disclosure. User interface 500 illustrates a map that can bepresented, for example, on a device display. User interface 500 includesindicators of three locations (550, 552, and 560) associated with thelocations of UEs in a friend-type relationship with the deviceassociated with the display presenting user interface 500.

Location indicator 550 can be an indicator of a location for a UE in afirst event driven permissive sharing of information relationship.Indicator 550 can be associated with the level of granularity designatedfor the information associated with the first event driven permissivesharing of information relationship. As an example, where the level ofgranularity is designated as no finer than a 100 meter radius, then theindicator would be expected to indicate a location within 100 meters ofthe actual location of the device in the first event driven permissivesharing of information relationship. Further, where an event triggeroccurs, the location information associated with indicator 550 canbecome stale where the location information is not further updated as aresult of restricting access to the shared information for the firstevent driven permissive sharing of information relationship.

Location indicator 552 can be an indicator of a location for a UE in asecond event driven permissive sharing of information relationship.Indicator 552 can be associated with the level of granularity designatedfor the information associated with the second event driven permissivesharing of information relationship. As an example, where the level ofgranularity is designated as no finer than indicating a city, then theindicator would be expected to indicate a location within the city thatthe device is in, for the second event driven permissive sharing ofinformation relationship.

Location indicator 560 can be an indicator of a location for a UE in amore conventional permissive sharing of information relationship.Indicator 560 can be associated with a level of granularity designatedfor the information associated with the more conventional long-terminformation sharing relationship. Moreover, where the more conventionallong-term information sharing relationship is not associated withtrigger events, indicator 560 would be expected to remain up to dateunder normal conditions. Location indicator 560 can be presentedsimultaneously with location indicators for event driven permissivesharing of information relationship, e.g., 550 and 552, illustratingthat the disclosed subject matter can be backwards compatible withlegacy information sharing services.

In view of the example system(s) described above, example method(s) thatcan be implemented in accordance with the disclosed subject matter canbe better appreciated with reference to flowcharts in FIG. 6-FIG. 8. Forpurposes of simplicity of explanation, example methods disclosed hereinare presented and described as a series of acts; however, it is to beunderstood and appreciated that the claimed subject matter is notlimited by the order of acts, as some acts may occur in different ordersand/or concurrently with other acts from that shown and describedherein. For example, one or more example methods disclosed herein couldalternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, interaction diagram(s) mayrepresent methods in accordance with the disclosed subject matter whendisparate entities enact disparate portions of the methodologies.Furthermore, not all illustrated acts may be required to implement adescribed example method in accordance with the subject specification.Further yet, two or more of the disclosed example methods can beimplemented in combination with each other, to accomplish one or moreaspects herein described. It should be further appreciated that theexample methods disclosed throughout the subject specification arecapable of being stored on an article of manufacture (e.g., acomputer-readable medium) to allow transporting and transferring suchmethods to computers for execution, and thus implementation, by aprocessor or for storage in a memory.

FIG. 6 illustrates aspects of a method 600 facilitating event drivenpermissive sharing of information in accordance with aspects of thesubject disclosure. At 610, a temporary friend sharing (TFS) profilevalue can be designated. TFS profile values can include values composinga TFS profile. The TFS profile can define, at least in part, aspects ofevent driven permissive sharing of information. The TFS profile can bestored on a UE or can be stored on a remote system, such as acarrier-side component. The TFS profile can include designation oftrigger event value. A trigger event value can be correlated withautomatically transitioning between permitting sharing of designatedinformation and restricting sharing of designated information. As anexample, where sharing location information is associated with atemporal trigger event value, sharing of the location information canoccur before the trigger time is reached and sharing of the locationinformation can be restricted after the trigger time is reached. Assuch, the TFS profile can facilitate designating temporary sharing oflocation information relationships.

At 620, a TFS permission value can be designated. The designated TFSpermission value can be based on the TFS profile value and a triggervalue. As an example, where a TFS profile value is associated with atarget UE and a trigger value is designated as 12 hours, a TFSpermission value can be designated that facilitates allowing the targetUE to access shared information. Further, notwithstanding otherconsiderations, it can be expected that the TFS permission value willcontinue to facilitate access to for the target UE to shared informationfor 12 hours.

At 630, access to information can be facilitated. The information to beaccessed can be designated as sharable information. Moreoverfacilitating access can be based on the TFS permission value from 620.At this point, method 600 can end.

In some embodiments, other TFS profile values can be designated. In anaspect, designating other TFS profile values can be correlated todesignating a TFS profile. A TFS profile can include designation of whatinformation can be shared, who or what can access information designatedfor sharing, and one or more trigger values. As an example, a profilecan designate values corresponding to allowing an employer to accesslocation information for a contract employee's UE until the contract iscompleted, i.e., the trigger value is an indicator of a completedcontract or a date on which the contract is designated to complete. Inother embodiments, predefined TFS profile schemes can be employed tofacilitate application of TFS profile(s) to event driven permissivesharing of information relationships in accordance with aspects of thesubject disclosure.

FIG. 7 illustrates a method 700 that facilitates event driven permissivesharing of information in accordance with aspects of the subjectdisclosure. At 710, a TFS profile value can be designated. At 720, a TFSpermission value can be designated. The designated TFS permission valuecan be based on the TFS profile value and a trigger value. At 730,access to information can be facilitated. The information to be accessedcan be designated as sharable information. Moreover facilitating accesscan be based on the TFS permission value from 720.

At 740, the value of the TFS permission value can be updated. Theupdating can be in response to a target value meeting a pre-definedcondition with respect to the trigger value. In an aspect this can beconsidered automatically updating the TFS permission value. At thispoint, method 700 can end. Updating the TFS permission value can beassociated with restricting access to information designated as sharableinformation. In an aspect, by updating the TFS permission value, accessto shared information can be restricted without needing to delete orotherwise alter an associated TFS profile. This can be helpful byallowing a user to update a trigger value with the correspondingautomatic update of the TFS permission value to reestablish access toshared information without having to input a TFS profile again toreestablish the event driven permissive sharing of information inaccordance with aspects of the subject disclosure. Further, where thereis integration into other systems of a UE, for example, an address booksystem (see FIG. 4 for example), an expired trigger value can rapidly belocated an updated with just a few taps of a corresponding informationand interaction segment. In another aspect, the TFS profile can beremoved to restrict access to shared information.

FIG. 8 illustrates an exemplary method 800 that facilitates event drivenpermissive sharing of location information in accordance with aspects ofthe subject disclosure. At 810, a TFS profile value can be designated ata first UE. At 820, a TFS permission value can be designated at acarrier-side component that is communicatively coupled to the first UE.Carrier-side components can be components that are part of a carriernetwork or are closely associated therewith. The designated TFSpermission value can be based on the TFS profile value and a temporaltrigger value. At 830, access to location information associated withthe first UE can be facilitated. The location information to be accessedcan be designated as sharable information. Moreover facilitating accesscan be based on the TFS permission value from 820. As an example, at830, a second UE can access location information associated with thefirst UE. In an aspect this can be associated with the first UEproviding location information designated as sharable information to acarrier-side system whereby the second UE can seek access to thelocation information by presenting credentials to the carrier-sidesystem that correspond to the TFS permission value from 820. Continuingthe example, the location information for the first UE can then be madeaccessible to the second UE.

At 840, the value of the TFS permission value can be updated. Theupdating can be in response to a clock value meeting a pre-definedcondition with respect to the temporal trigger value. At this point,method 800 can end. Updating the TFS permission value can be associatedwith restricting access to location information designated as sharableinformation.

FIG. 9 presents an example embodiment 900 of a mobile network platform910 that can implement and exploit one or more aspects of the subjectinnovation described herein. Generally, wireless network platform 910can include components, e.g., nodes, gateways, interfaces, servers, ordisparate platforms, that facilitate both packet-switched (PS) (e.g.,internet protocol (IP), frame relay, asynchronous transfer mode (ATM))and circuit-switched (CS) traffic (e.g., voice and data), as well ascontrol generation for networked wireless telecommunication. As anon-limiting example, wireless network platform 910 can be included intelecommunications carrier networks, and can be considered carrier-sidecomponents as discussed elsewhere herein. Mobile network platform 910includes CS gateway node(s) 912 which can interface CS traffic receivedfrom legacy networks like telephony network(s) 940 (e.g., publicswitched telephone network (PSTN), or public land mobile network (PLMN))or a signaling system #7 (SS7) network 970. Circuit switched gatewaynode(s) 912 can authorize and authenticate traffic (e.g., voice) arisingfrom such networks. Additionally, CS gateway node(s) 912 can accessmobility, or roaming, data generated through SS7 network 970; forinstance, mobility data stored in a visited location register (VLR),which can reside in memory 930. Moreover, CS gateway node(s) 912interfaces CS-based traffic and signaling and PS gateway node(s) 918. Asan example, in a 3GPP UMTS network, CS gateway node(s) 912 can berealized at least in part in gateway GPRS support node(s) (GGSN). Itshould be appreciated that functionality and specific operation of CSgateway node(s) 912, PS gateway node(s) 918, and serving node(s) 916, isprovided and dictated by radio technology(ies) utilized by mobilenetwork platform 910 for telecommunication.

In addition to receiving and processing CS-switched traffic andsignaling, PS gateway node(s) 918 can authorize and authenticatePS-based data sessions with served mobile devices. Data sessions caninclude traffic, or content(s), exchanged with networks external to thewireless network platform 910, like wide area network(s) (WANs) 950,enterprise network(s) 970, and service network(s) 980, which can beembodied in local area network(s) (LANs), can also be interfaced withmobile network platform 910 through PS gateway node(s) 918. It is to benoted that WANs 950 and enterprise network(s) 960 can embody, at leastin part, a service network(s) like IP multimedia subsystem (IMS). Basedon radio technology layer(s) available in technology resource(s) 917,packet-switched gateway node(s) 918 can generate packet data protocolcontexts when a data session is established; other data structures thatfacilitate routing of packetized data also can be generated. To thatend, in an aspect, PS gateway node(s) 918 can include a tunnel interface(e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (notshown)) which can facilitate packetized communication with disparatewireless network(s), such as Wi-Fi networks.

In embodiment 900, wireless network platform 910 also includes servingnode(s) 916 that, based upon available radio technology layer(s) withintechnology resource(s) 917, convey the various packetized flows of datastreams received through PS gateway node(s) 918. It is to be noted thatfor technology resource(s) 917 that rely primarily on CS communication,server node(s) can deliver traffic without reliance on PS gatewaynode(s) 918; for example, server node(s) can embody at least in part amobile switching center. As an example, in a 3GPP UMTS network, servingnode(s) 916 can be embodied in serving GPRS support node(s) (SGSN).

For radio technologies that exploit packetized communication, server(s)914 in wireless network platform 910 can execute numerous applicationsthat can generate multiple disparate packetized data streams or flows,and manage (e.g., schedule, queue, format . . . ) such flows. Suchapplication(s) can include add-on features to standard services (forexample, provisioning, billing, customer support . . . ) provided bywireless network platform 910. Data streams (e.g., content(s) that arepart of a voice call or data session) can be conveyed to PS gatewaynode(s) 918 for authorization/authentication and initiation of a datasession, and to serving node(s) 916 for communication thereafter. Inaddition to application server, server(s) 914 can include utilityserver(s), a utility server can include a provisioning server, anoperations and maintenance server, a security server that can implementat least in part a certificate authority and firewalls as well as othersecurity mechanisms, and the like. In an aspect, security server(s)secure communication served through wireless network platform 910 toensure network's operation and data integrity in addition toauthorization and authentication procedures that CS gateway node(s) 912and PS gateway node(s) 918 can enact. Moreover, provisioning server(s)can provision services from external network(s) like networks operatedby a disparate service provider; for instance, WAN 950 or GlobalPositioning System (GPS) network(s) (not shown). Provisioning server(s)can also provision coverage through networks associated to wirelessnetwork platform 910 (e.g., deployed and operated by the same serviceprovider), such as femto-cell network(s) (not shown) that enhancewireless service coverage within indoor confined spaces and offload RANresources in order to enhance subscriber service experience within ahome or business environment by way of UE 975.

It is to be noted that server(s) 914 can include one or more processorsconfigured to confer at least in part the functionality of macro networkplatform 910. To that end, the one or more processor can execute codeinstructions stored in memory 930, for example. It is should beappreciated that server(s) 914 can include a content manager 915, whichoperates in substantially the same manner as described hereinbefore.

In example embodiment 900, memory 930 can store information related tooperation of wireless network platform 910. Other operationalinformation can include provisioning information of mobile devicesserved through wireless platform network 910, subscriber databases;application intelligence, pricing schemes, e.g., promotional rates,flat-rate programs, couponing campaigns; technical specification(s)consistent with telecommunication protocols for operation of disparateradio, or wireless, technology layers; and so forth. Memory 930 can alsostore information from at least one of telephony network(s) 940, WAN950, enterprise network(s) 960, or SS7 network 970. In an aspect, memory930 can be, for example, accessed as part of a data store component oras a remotely connected memory store.

In order to provide a context for the various aspects of the disclosedsubject matter, FIG. 10, and the following discussion, are intended toprovide a brief, general description of a suitable environment in whichthe various aspects of the disclosed subject matter can be implemented.While the subject matter has been described above in the general contextof computer-executable instructions of a computer program that runs on acomputer and/or computers, those skilled in the art will recognize thatthe subject innovation also can be implemented in combination with otherprogram modules. Generally, program modules include routines, programs,components, data structures, etc. that perform particular tasks and/orimplement particular abstract data types.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory, by way of illustration, and not limitation, volatilememory 1020 (see below), non-volatile memory 1022 (see below), diskstorage 1024 (see below), and memory storage 1046 (see below). Further,nonvolatile memory can be included in read only memory (ROM),programmable ROM (PROM), electrically programmable ROM (EPROM),electrically erasable ROM (EEPROM), or flash memory. Volatile memory caninclude random access memory (RAM), which acts as external cache memory.By way of illustration and not limitation, RAM is available in manyforms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronousDRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM(ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM).Additionally, the disclosed memory components of systems or methodsherein are intended to comprise, without being limited to comprising,these and any other suitable types of memory.

Moreover, it will be noted that the disclosed subject matter can bepracticed with other computer system configurations, includingsingle-processor or multiprocessor computer systems, mini-computingdevices, mainframe computers, as well as personal computers, hand-heldcomputing devices (e.g., PDA, phone, watch, tablet computers, netbookcomputers, . . . ), microprocessor-based or programmable consumer orindustrial electronics, and the like. The illustrated aspects can alsobe practiced in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network; however, some if not all aspects of the subjectdisclosure can be practiced on stand-alone computers. In a distributedcomputing environment, program modules can be located in both local andremote memory storage devices.

FIG. 10 illustrates a block diagram of a computing system 1000 operableto execute the disclosed systems and methods in accordance with anembodiment. Computer 1012, which can be, for example, part of thehardware of a UE (e.g., 110, 210, 310, etc.), a carrier-side component,etc., includes a processing unit 1014, a system memory 1016, and asystem bus 1018. System bus 1018 couples system components including,but not limited to, system memory 1016 to processing unit 1014.Processing unit 1014 can be any of various available processors. Dualmicroprocessors and other multiprocessor architectures also can beemployed as processing unit 1014.

System bus 1018 can be any of several types of bus structure(s)including a memory bus or a memory controller, a peripheral bus or anexternal bus, and/or a local bus using any variety of available busarchitectures including, but not limited to, Industrial StandardArchitecture (ISA), Micro-Channel Architecture (MSA), Extended ISA(EISA), Intelligent Drive Electronics, VESA Local Bus (VLB), PeripheralComponent Interconnect (PCI), Card Bus, Universal Serial Bus (USB),Advanced Graphics Port (AGP), Personal Computer Memory CardInternational Association bus (PCMCIA), Firewire (IEEE 1194), and SmallComputer Systems Interface (SCSI).

System memory 1016 can include volatile memory 1020 and nonvolatilememory 1022. A basic input/output system (BIOS), containing routines totransfer information between elements within computer 1012, such asduring start-up, can be stored in nonvolatile memory 1022. By way ofillustration, and not limitation, nonvolatile memory 1022 can includeROM, PROM, EPROM, EEPROM, or flash memory. Volatile memory 1020 includesRAM, which acts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as SRAM, dynamic RAM(DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM),enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), Rambus direct RAM(RDRAM), direct Rambus dynamic RAM (DRDRAM), and Rambus dynamic RAM(RDRAM).

Computer 1012 can also include removable/non-removable,volatile/non-volatile computer storage media. FIG. 10 illustrates, forexample, disk storage 1024. Disk storage 1024 includes, but is notlimited to, devices like a magnetic disk drive, floppy disk drive, tapedrive, flash memory card, or memory stick. In addition, disk storage1024 can include storage media separately or in combination with otherstorage media including, but not limited to, an optical disk drive suchas a compact disk ROM device (CD-ROM), CD recordable drive (CD-R Drive),CD rewritable drive (CD-RW Drive) or a digital versatile disk ROM drive(DVD-ROM). To facilitate connection of the disk storage devices 1024 tosystem bus 1018, a removable or non-removable interface is typicallyused, such as interface 1026.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

It can be noted that FIG. 10 describes software that acts as anintermediary between users and computer resources described in suitableoperating environment 1000. Such software includes an operating system1028 (e.g., OS component(s) 312, etc.) Operating system 1028, which canbe stored on disk storage 1024, acts to control and allocate resourcesof computer system 1012. System applications 1030 take advantage of themanagement of resources by operating system 1028 through program modules1032 and program data 1034 stored either in system memory 1016 or ondisk storage 1024. It is to be noted that the disclosed subject mattercan be implemented with various operating systems or combinations ofoperating systems.

A user can enter commands or information into computer 1012 throughinput device(s) 1036. As an example, user interface 400 and 500 can beembodied in a touch sensitive display panel allowing a user to interactwith computer 1012 such as by tapping section 410, 412, or 414, etc.Input devices 1036 include, but are not limited to, a pointing devicesuch as a mouse, trackball, stylus, touch pad, keyboard, microphone,joystick, game pad, satellite dish, scanner, TV tuner card, digitalcamera, digital video camera, web camera, cell phone, smartphone, tabletcomputer, etc. These and other input devices connect to processing unit1014 through system bus 1018 by way of interface port(s) 1038. Interfaceport(s) 1038 include, for example, a serial port, a parallel port, agame port, a universal serial bus (USB), an infrared port, a Bluetoothport, an IP port, or a logical port associated with a wireless service,etc. Output device(s) 1040 use some of the same type of ports as inputdevice(s) 1036.

Thus, for example, a USB port can be used to provide input to computer1012 and to output information from computer 1012 to an output device1040. Output adapter 1042 is provided to illustrate that there are someoutput devices 1040 like monitors, speakers, and printers, among otheroutput devices 1040, which use special adapters. Output adapters 1042include, by way of illustration and not limitation, video and soundcards that provide means of connection between output device 1040 andsystem bus 1018. It should be noted that other devices and/or systems ofdevices provide both input and output capabilities such as remotecomputer(s) 1044.

Computer 1012 can operate in a networked environment using logicalconnections to one or more remote computers, such as remote computer(s)1044. Remote computer(s) 1044 can be a personal computer, a server, arouter, a network PC, cloud storage, cloud service, a workstation, amicroprocessor based appliance, a peer device, or other common networknode and the like, and typically includes many or all of the elementsdescribed relative to computer 1012.

For purposes of brevity, only a memory storage device 1046 isillustrated with remote computer(s) 1044. Remote computer(s) 1044 islogically connected to computer 1012 through a network interface 1048and then physically connected by way of communication connection 1050.Network interface 1048 encompasses wire and/or wireless communicationnetworks such as local-area networks (LAN) and wide-area networks (WAN).LAN technologies include Fiber Distributed Data Interface (FDDI), CopperDistributed Data Interface (CDDI), Ethernet, Token Ring and the like.WAN technologies include, but are not limited to, point-to-point links,circuit switching networks like Integrated Services Digital Networks(ISDN) and variations thereon, packet switching networks, and DigitalSubscriber Lines (DSL). As noted below, wireless technologies may beused in addition to or in place of the foregoing.

Communication connection(s) 1050 refer(s) to hardware/software employedto connect network interface 1048 to bus 1018. While communicationconnection 1050 is shown for illustrative clarity inside computer 1012,it can also be external to computer 1012. The hardware/software forconnection to network interface 1048 can include, for example, internaland external technologies such as modems, including regular telephonegrade modems, cable modems and DSL modems, ISDN adapters, and Ethernetcards.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor may also be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Moreover, terms like “user equipment (UE),” “mobile station,” “mobile,”subscriber station,” “subscriber equipment,” “access terminal,”“terminal,” “handset,” and similar terminology, refer to a wirelessdevice utilized by a subscriber or user of a wireless communicationservice to receive or convey data, control, voice, video, sound, gaming,or substantially any data-stream or signaling-stream. The foregoingterms are utilized interchangeably in the subject specification andrelated drawings. Likewise, the terms “access point (AP),” “basestation,” “Node B,” “evolved Node B (eNode B),” “home Node B (HNB),”“home access point (HAP),” and the like, are utilized interchangeably inthe subject application, and refer to a wireless network component orappliance that serves and receives data, control, voice, video, sound,gaming, or substantially any data-stream or signaling-stream to and froma set of subscriber stations or provider enabled devices. Data andsignaling streams can include packetized or frame-based flows.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. UEs do not normally connect directly to thecore networks of a large service provider but can be routed to the coreby way of a switch or radio area network. Authentication can refer todeterminations regarding whether the user requesting a service from thetelecom network is authorized to do so within this network or not. Callcontrol and switching can refer determinations related to the futurecourse of a call stream across carrier equipment based on the callsignal processing. Charging can be related to the collation andprocessing of charging data generated by various network nodes. Twocommon types of charging mechanisms found in present day networks can beprepaid charging and postpaid charging. Service invocation can occurbased on some explicit action (e.g. call transfer) or implicitly (e.g.,call waiting). It is to be noted that service “execution” may or may notbe a core network functionality as third party network/nodes may takepart in actual service execution. A gateway can be present in the corenetwork to access other networks. Gateway functionality can be dependenton the type of the interface with another network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks include Geocasttechnology; broadcast technologies (e.g., sub-Hz, ELF, VLF, LF, MF, HF,VHF, UHF, SHF, THz broadcasts, etc.); Ethernet; X.25; powerline-typenetworking (e.g., PowerLine AV Ethernet, etc.); femto-cell technology;Wi-Fi; Worldwide Interoperability for Microwave Access (WiMAX); EnhancedGeneral Packet Radio Service (Enhanced GPRS); Third GenerationPartnership Project (3GPP or 3G) Long Term Evolution (LTE); 3GPPUniversal Mobile Telecommunications System (UMTS) or 3GPP UMTS; ThirdGeneration Partnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB);High Speed Packet Access (HSPA); High Speed Downlink Packet Access(HSDPA); High Speed Uplink Packet Access (HSUPA); GSM Enhanced DataRates for GSM Evolution (EDGE) Radio Access Network (RAN) or GERAN; UMTSTerrestrial Radio Access Network (UTRAN); or LTE Advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methodologieshere. One of ordinary skill in the art may recognize that many furthercombinations and permutations of the claimed subject matter arepossible. Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

What is claimed is:
 1. A system, comprising: a processor; and a memorythat stores executable instructions that, when executed by theprocessor, facilitate performance of operations, comprising: receivingidentity data representative of a user identity and an adjustabletemporal-expiration value associated with temporal control of access tosharable data associated with the user identity, wherein the adjustabletemporal-expiration value is adjusted in response to receiving anupdated time value via an interface of a user equipment associated withthe user identity, and wherein the adjustable temporal-expiration valueis stored in a profile of the user identity; determining the sharabledata associated with the profile; updating a permission value inresponse to a first value related to a device other than the userequipment being determined to have transitioned a trigger value, whereinthe trigger value corresponds to a selectable spatial condition storedin the profile of the user identity; and enabling access to a portion ofthe sharable data at a selectable granularity, for the device other thanthe user equipment, based on the permission value and based on theadjustable temporal-expiration value being determined to satisfy a rulerelated to the permission value, wherein the selectable granularity isstored in the profile of the user identity.
 2. The system of claim 1,wherein the first value is a distance value associated with a distancebetween the device and a boundary represented via the trigger value. 3.The system of claim 1, wherein the first value is a proximity valueassociated with a proximity of the device and a location represented viathe trigger value.
 4. The system of claim 1, wherein the first value isa location value associated with a comparing a location of the devicewith a location represented via the trigger value.
 5. The system ofclaim 1, wherein the first value is a speed value associated with aspeed of the device and a speed represented via the trigger value. 6.The system of claim 1, wherein the operations further comprise updatingthe permission value in response to determining a rule related tohierarchical access to the subset of sharable data has been satisfied.7. The system of claim 1, wherein the operations further compriseupdating the permission value in response to determining a rule relatedto allowing access to the subset of sharable data based on auser-identified relationship has been satisfied.
 8. The system of claim1, wherein the subset of the sharable data is determined based onsharable location information.
 9. The system of claim 1, wherein thesubset of the sharable data is determined based on sharable scheduleinformation.
 10. The system of claim 1, wherein the subset of thesharable data is determined based on sharable user equipment serviceinformation.
 11. A method, comprising: accessing, by a system comprisinga processor, a sharing profile associated with an entity; determining,by the system, sharable data that is accessible at a selectablegranularity designated in the sharing profile; in response to thesharing profile comprising a selectable target spatial condition valueassociated with a user identity, designating, by the system, apermission value based on the selectable target spatial condition of thesharing profile and a position of a target device; and facilitating, bythe system, access to the sharable data in response to a selectabletemporal condition related to time-limited access to the shareable databeing determined to have satisfied a rule related to the permissionvalue, wherein the selectable temporal condition is stored in thesharing profile and is adjusted in response to receiving an updated timeof access value via a user interface of a user equipment associated withthe entity.
 12. The method of claim 11, wherein the updating thepermission value based on the selectable target spatial condition of thesharing profile comprises determining a distance value associated with adistance between the target device and a selectable boundary.
 13. Themethod of claim 11, wherein the updating the permission value based onthe selectable target spatial condition of the sharing profile comprisesdetermining a proximity value associated with a proximity of the targetdevice to a selectable location.
 14. The method of claim 11, wherein theupdating the permission value based on the selectable target spatialcondition of the sharing profile comprises determining a location valueassociated with comparing a location of the target device to aselectable location.
 15. The method of claim 11, wherein the updatingthe permission value based on the selectable target spatial condition ofthe sharing profile comprises determining a speed value associated witha speed of the target device.
 16. A mobile device, comprising: aprocessor; and a memory that stores executable instructions that, whenexecuted by the processor, facilitate performance of operations,comprising: receiving input corresponding to an information sharingprofile associated with a user identity determined to be associated witha device other than the mobile device; assigning, to a first value ofthe information sharing profile, a selectable spatial condition valuerelated to a spatial characteristic of the device in response toreceiving a spatial condition value associated with the user identityvia an interface of the mobile device; assigning, to a second value ofthe information sharing profile, a sharable information designationvalue related to designating information related to the user identity assharable information in response to receiving an information designationvalue associated with the user identity via the interface of the mobiledevice; assigning, to a third value of the information sharing profile,a sharable information granularity value related to designating a levelof data granularity associated with the sharable information in responseto receiving an information granularity value associated with the useridentity via the interface of the mobile device; updating a permissionvalue in response to the first value being determined to have satisfieda designated spatial condition, wherein the permission value isassociated with an updatable temporal-expiration condition, the firstvalue, the second value, and the third value, and wherein the updatabletemporal-expiration value is adjusted in response to receiving anupdated time value associated with the user identity via the interfaceof the mobile device; and enabling access to a portion of the sharableinformation related to the user identity based on the permission value,wherein the access is via the device other than the mobile device. 17.The mobile device of claim 16, wherein the first value is a distancevalue associated with a distance between the device and a boundary. 18.The mobile device of claim 16, wherein the mobile device is a firstdevice, wherein the device is a second device, and wherein the firstvalue is a proximity value associated with a proximity of the device toa third device.
 19. The mobile device of claim 16, wherein the firstvalue is a location value associated with a location of the device. 20.The mobile device of claim 16, wherein the first value is a speed valueassociated with a speed of the device.